
<HTML><HEAD><TITLE>Manpage of socks</TITLE>
</HEAD><BODY>
<H1>socks</H1>
Section: Universal proxy server (8)<BR>Updated: July 2009<BR><A HREF="#index">Index</A>
<A HREF="../index.html">Return to Main Contents</A><HR>

<A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2>

<B>socks</B>

- SOCKS 4/4.5/5 gateway service
<A NAME="lbAC">&nbsp;</A>
<H2>SYNOPSIS</H2>

<B>socks </B>[<B>-d</B>]

<I></I>[<B>-l</B><I></I>[<B></B>[<I>@</I><B></B>]<I>logfile</I><B></B>]]

<I></I>[<B>-p</B><I>port</I>]

<I></I>[<B>-i</B><I>internal_ip</I>]

<I></I>[<B>-e</B><I>external_ip</I>]

<A NAME="lbAD">&nbsp;</A>
<H2>DESCRIPTION</H2>

<B>socks</B>

is SOCKS server. It supports SOCKSv4, SOCKSv4.5 (extension to v4 for
server side name resolution) and SOCKSv5. SOCKSv5 specification allows both
outgoing and reverse TCP connections and UDP portmapping.
<A NAME="lbAE">&nbsp;</A>
<H2>OPTIONS</H2>

<DL COMPACT>
<DT><B>-I</B>

<DD>
Inetd mode. Standalone service only.
<DT><B>-d</B>

<DD>
Daemonise. Detach service from console and run in the background.
<DT><B>-t</B>

<DD>
Be silenT. Do not log start/stop/accept error records.
<DT><B>-u</B>

<DD>
Never ask for username authentication
<DT><B>-e</B>

<DD>
External address. IP address of interface proxy should initiate connections
from. External IP must be specified if you need incoming connections.
By default system will deside which address to use in accordance
with routing table.
<DT><B>-i</B>

<DD>
Internal address. IP address proxy accepts connections to.
By default connection to any interface is accepted. It's usually unsafe.
<DT><B>-p</B>

<DD>
Port. Port proxy listens for incoming connections. Default is 1080.
<DT><B>-l</B>

<DD>
Log. By default logging is to stdout. If
<I>logfile</I>

is specified logging is to file. Under Unix, if
'<I>@</I>'

preceeds
<I>logfile</I>,

syslog is used for logging.
</DL>
<A NAME="lbAF">&nbsp;</A>
<H2>CLIENTS</H2>

You should use client with SOCKS support or use some socksification support
(for example
<I>SocksCAP</I>

or
<I>FreeCAP</I>).

Configure client to use
<I>internal_ip</I>

and
<I>port</I>.

SOCKS allows to use almost any application protocol without limitation. This
implementation also allows to open priviledged port on server (if socks has
sufficient privileges). If you need to control access use
<B><A HREF="../man8/3proxy.8.html">3proxy</A></B>(8)

instead.
<A NAME="lbAG">&nbsp;</A>
<H2>BUGS</H2>

Report all bugs to
<B><A HREF="mailto:3proxy@security.nnov.ru">3proxy@security.nnov.ru</A></B>

<A NAME="lbAH">&nbsp;</A>
<H2>SEE ALSO</H2>

<A HREF="../man8/3proxy.8.html">3proxy</A>(8), <A HREF="../man8/proxy.8.html">proxy</A>(8), <A HREF="../man8/ftppr.8.html">ftppr</A>(8), <A HREF="../man8/pop3p.8.html">pop3p</A>(8), <A HREF="../man8/tcppm.8.html">tcppm</A>(8), <A HREF="../man8/udppm.8.html">udppm</A>(8), <A HREF="../man8/syslogd.8.html">syslogd</A>(8),
<BR>

<A HREF="http://3proxy.ru/">http://3proxy.ru/</A>
<A NAME="lbAI">&nbsp;</A>
<H2>AUTHORS</H2>

3proxy is designed by 3APA3A
(<I><A HREF="mailto:3APA3A@security.nnov.ru">3APA3A@security.nnov.ru</A></I>),

Vladimir Dubrovin
(<I><A HREF="mailto:vlad@sandy.ru">vlad@sandy.ru</A></I>)

<P>

<HR>
<A NAME="index">&nbsp;</A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
<DT><A HREF="#lbAE">OPTIONS</A><DD>
<DT><A HREF="#lbAF">CLIENTS</A><DD>
<DT><A HREF="#lbAG">BUGS</A><DD>
<DT><A HREF="#lbAH">SEE ALSO</A><DD>
<DT><A HREF="#lbAI">AUTHORS</A><DD>
</DL>
<HR>
This document was created by
using the manual pages.<BR>
Time: 11:38:09 GMT, December 11, 2009
</BODY>
</HTML>
